PagerDuty

its best suited for the team which are operational heavy and where folks are situated around the globe, using pagerduty its easy to create follow the sun model for managing your on-call schedules and since its very popular and offer a good use-experience its easy to onboard new team members to pagerduty platform.

This is very useful for anyone looking to automate most of the monitoring/altering tasks, get AI based recommendations on alerts and reduce the need to people manually monitoring the INC queues. It also gives an option to get an overview of services impacted and stakeholders can get timely notifications. Incident response and resolution times are also reduced as only the right people are involved in the flow.

It is best suited for numerous Support Teams with different on-call schedules. That is the scenario where we use it - so it's hard to imagine any "less appropriate" scenarios.

Well Suited: On call teams getting alerted in a timely fashion. It eliminates the need to sit by your computer all night & day refreshing you screen. you know when you need to take action

No Appropriate: i dont see the need for it in my role to be used unless on call

We utilise PagerDuty to alert on-call staff of application failures, infrastructure issues. security alerts and on-call roster management. It's very versatile and has excellent integration options including the ability to establish unique email addresses for each service. Sending an email to that address will process this email and trigger an alert that corresponds to this email. Setting this up takes minimal time, and allows the scope of the product to be expanded dramatically.

We have also utilised the PagerDuty AI to aggregate alerts, reducing alert fatigue.

If an organization lacks consistency in how on-call operations are handled or does not have a centralized way to mobilize resources quickly then PagerDuty is a fantastic option. While the platform was not originally designed for managed service providers, it can be adopted and adjusted to support multiple customers and partners. For organizations with a larger resource footprint with a wide variety of skillsets, PagerDuty makes it a breeze to get organized and get the right people on the phone when it matters.

It is very good at consolidating alerting and having a centralized location for handling all alerting across all teams. It gives good flexibility in terms of user functionality. The escalation process seems to be very mature is very configurable. It seems limited in its ability to do complex routing of alerts, if you are wanting to rule based alerting that would need to be a feature based on the application that is triggering it and not some feature in PagerDuty.

In our stacks we want to monitor for things like extreme latency, CPU usage, Memory Usage, etc. and these monitors/metrics are then sent to PagerDuty when they break certain thresholds which then allows PagerDuty to send alerts only to the on-call engineer who can go look at the issue and troubleshoot/fix as needed.

PagerDuty is really well suited for support and engineering, getting an incident response team aware of what is going on -- especially after hours -- and it integrates really easily. For what the tool does, I don't know that there is a less suited use. Very happy with the alerting and the integrations.

Using pagerduty provides a SaaS solution ready to use, however, other (open source) solutions seem to be better suited such as the Elastic seach, Logstash and Kibana stack or Loki and Grafana. The main issue around pagerduty is the documentation. Once the documentation figured out, the implementation is pretty eazy.

PagerDuty is a great solution for large teams that require immediate action when things aren't going right. If your business needs urgent support provided to customers if your product fails, PagerDuty allows you to empower your team to only engage when a set of triggers are met. It also gives you back up layers to ensure issues are responded to, even if the main on-call person isn't able to be reached.

PagerDuty is great if you want a tool that integrates well with your existing infrastructure to provide digital forensics and incident responses. It is easy to set up, and has decent API integrations. It does a good job of notifying/escalating incidents to the right teams expediently, allowing for SMS, mobile app, and other options for notifying. It is also easy to set up and configure out of the box.
It's not the tool that allows for total granularity and control, but if you want that, you're probably better off building it in house. The UI and some reporting functionalities can be improved, but all in all its a solid tool for its convenience.

If you're running critical business infrastructure which requires constant monitoring and on-call management, PagerDuty is go to tool which helps in alerting, on-call schedules and integrates with business apps.

The product works very well. It was priced higher than it's competitors.

PagerDuty works great for all of our technology teams for important issue tracking but does not apply for the rest of our teams.

In case you want to get the right notifications to the right persons at the right time, PagerDuty enables you with maximum flexibility to do so. Not only will the developers be notified to solve the problems, but also management stakeholders can be informed and kept in the loop during the root cause analysis and hot fix deployment such that everyone is on the same page all the time.

Really strong, well-designed notification system. Good reliable software. I have used PD at two different employers and have also programmed notifications for PD in Python. The API was solid, straightforward, forward and simple, yet it provided the ability for more complex and robust functionality.

This is well suited to businesses who want an automated solution to inform someone when an issue arises, this can be a problem for many companies who run a 24/7 uptime service. For us this feeds into our business 24/7 escalation procedure, we have full automation, from monitoring to firing off events to fix or gather data to attach to a PagerDuty alert which engages the engineer and escalates if there is no reply along with raising an entry in our ticketing system and also embedding the data into that already for the engineer to sign off once they have logged in and done the relevant work. PagerDuty has reduced our costs in terms of staff and has allowed our IT staff to have more human-friendly hours instead of shifts which were until 10 pm in the evening from 6 am in the morning. It also bridges the gap between 10 pm and 6 am in terms of, we don't have to rely on somebody from a non-IT department noticing that there is an issue on the alert monitor as well as them not understanding what it is they are seeing. This is now an essential part of our automation system and has made the out-of-hours escalation process so much smoother.

Rundeck is a really good solution to formalize , standardize and automate your infrastructure operational run book. It can be also used in combination with your monitoring solution to auto heal your services. As for example when you get a specific alert, instead of triggering your notification channel to first trigger the Rundeck job to try and fix the issues (service restart etc..) and only then if the problem still persist to escalate and notify through an alert. It is also super handy to run all tasks from a central location and making sure there is no other person running the same job on the same servers at the same time, been able to see statistic about how fast or successful a job runs is also a big plus.

I'm sure most IT support organizations need to use this tool or one like it to be able to alert people for assistance in outage situations. Multiple times we have had servers or even network devices giving us trouble and degrading service to our end customers. I am usually one of the multi-team staff that get paged to check devices for power, activity lights, and/or error logging. Not sure what else to say here. It's pretty straight forward to me.

PagerDuty is best suited for reaching out to the on-call support team in case of urgent issues. we can set up a call schedule for different team members working from different locations. One can easily push notification and individuals gets notification based on their alert rules. this allows the team to jump on quickly and saves a lot of precious time. this results in eventually faster resolution of urgent issues and customer satisfaction.

It works great when managing an on-call rotation and having people on-call, especially in a corporate setting with multiple teams. It works well for issues with software and hardware being down, as well as network equipment. Works great with integration and accepts alerts via email, API, slack, etc. It may be less appropriate in very small settings where only one person is on-call.

Great for both large and small teams with a lot of features and customization. Also since it's so popular, pretty much every major monitoring system integrates with it. API setup is very easy. The only environments where it might not be necessary are non-critical operations or where IT support is minimal, given it is significantly complicated to set up beyond the most basic use case; however, once it is set up properly, it is mostly set-it-and-forget-it.

The alerts are super reliable, which is important. It is good to be able to configure a few layers of "on-call" shifts because it might be "bad" to alert everyone if someone is too slow to hit the ACK button.

Historically, I would be a 10 on PagerDuty. I have used PD for a very long time at multiple companies. However with our recent pain, while attempting to implement response [plans] as a way to notify multiple parties without stopping escalation policies or notification preferences, the highest I can go is a 6. The reason for the 6 is I know that this is an NPS survey and 7/8 is thrown out. I'm not a promoter at this time and am barely a detractor. If PD provides a solution to response play pain that we are experiencing, I'll be back at a 10.